Hi everyone,

 

I'm currently reviewing the retention times for each data set in our Data Warehouse and have read Kevin Holman's blog that covers the topic quite comprehensively (http://blogs.technet.com/b/kevinholman/archive/2010/01/05/understanding-and-modifying-data-warehouse-retention-and-grooming.aspx).

Towards the end of the blog, Kevin mentions "Most people don't do a lot of state reporting beyond 30 days, and these can be groomed much sooner as well if desired. "

So my question is - what is the State Data Set actually used for? Before I can make a decision on what the retention time should be, I need to know what kind of reports this is used in and therefore if we use it... Does anyone have some examples?

 

Thanks guys,

Kristian

Hi Kristian,

State data used for:

- Availability reports

- Service Level Tracking \ Reporting

I might have been a bit too agressive when I said 30 days.  That was just an example really.  Now - most customers I work with only look at availability reports for the past month, and sometimes past quarter.

A more reasonable approach might be 30 days for raw, 90 days for hourly, and 180 days for daily.  It just depends on which reports you use/plan to use, and how granular you need that data to be.

• Marked as answer by Nicholas LiModerator Friday, July 30, 2010 7:20 AM

I might have been a bit too agressive when I said 30 days.  That was just an example really.  Now - most customers I work with only look at availability reports for the past month, and sometimes past quarter.

A more reasonable approach might be 30 days for raw, 90 days for hourly, and 180 days for daily.  It just depends on which reports you use/plan to use, and how granular you need that data to be.

• Marked as answer by Nicholas LiModerator Friday, July 30, 2010 7:20 AM

State data written directly to the data warehouse summarizes by object the time that object was in a specific state. This information is aggregated into units of hours and sub-hours.